home *** CD-ROM | disk | FTP | other *** search
- In <JARIS.94Mar27145118@vipunen.hut.fi> jaris@vipunen.hut.fi (Jari M I Salminen) writes:
-
- >Here's how I got MS TCP/32 to work with WFW 3.11, ODI/NDIS3 and Intel
- >EtherExpress 16:
-
- >The MS TCP/32 installation inserted line "Binding=ms$ee16" into [ms$ee160]
- >section in SYSTEM.INI. However, since I use ODI, the [ms$ee16] section
- >in PROTOCOL.INI is empty and MS TCP/32 could not work.
-
- >I noticed that some other sections in PROTOCOL.INI (such as [NETBEUI] and
- >[NWLINK]) had a line "BINDINGS=EXP16ODI", so I tried that for
- >the SYSTEM.INI setting. And with line "Binding=EXP16ODI" in SYSTEM.INI
- >MS TCP/32 works (haven't tested that much but the ftp seems to be
- >operational).
-
- It other words, set Binding to the name of your MLID, in my case 3C509.
- A slight bug in the installation procedure, I'd say.
-
- >Note also that there is also a section [MSTCP32] in PROTOCOL.INI which
- >has a line "BINDINGS=EXP16ODI". I'm not sure if I changed that or was it
- >the MS TCP/32 installation program, but I guess it must be there...
-
- Installation program did that all by itself.
-
- >Hope this helps.
-
- It certainly did. Thanks. Tarkat silm{t sinulla.
-
- > Jari
-
- Hannu
-
-